ℹ️ Modified Workflows

This pull request contains modified workflow files and no preview will be created.

Workflow files modified:

• .github/workflows/README.md
• .github/workflows/sandpaper-version.txt

If this is not from a trusted source, please inspect the changes for any malicious content.

Hi Hugo, thank you for looking up on this.

I'll ask questions here and then proceed to approve the merging in the other repos:

• These are automated builds, as I read in the PR comment. How do you run it?
• In the following iterations, how should we run these updates?

Reference documentation:

• https://carpentries.github.io/sandpaper-docs/pull-request.html#automated-pull-requests
• https://carpentries.github.io/sandpaper/articles/automated-pull-requests.html#setting-up-a-pull-request-bot

They will run automatically each week or each month depending on the workflow.

I've exceptionally triggered them manually via https://docs.github.com/en/actions/using-workflows/manually-running-a-workflow.

They will run automatically each week or each month depending on the workflow.

I've exceptionally triggered them manually via https://docs.github.com/en/actions/using-workflows/manually-running-a-workflow.

Nice to see where the workflow is configured.

As far as I've been following the workflow actions, they have been running automatically since the start of the repository with that frequency. examples for package cache and workflow updates

But this manual trigger was exceptional. This created a PR.

• Should we now expect to receive these automated PRs?
• Should we do this manual triggering with a certain frequency away from the monthly and weekly frequency?

Should we now expect to receive these automated PRs?

Yes, because I have created the missing token and added it as a secret to the relevant repositories.

Should we do this manual triggering with a certain frequency away from the monthly and weekly frequency?

No, it's probably not necessary. I've done it this time to test that the token was working correctly and to ensure potential issues are fixed ASAP since we went a long time without updating the infrastructure.

ready to merge 🚀